Feature activation control and data prefetching with network-connected mobile devices

ABSTRACT

In some embodiments, an electronic device is disclosed for intelligently prefetching data via a computer network. The electronic device can include a device housing, a user interface, a memory device, and a hardware processor. The hardware processor can: communicate via a communication network; determine that the hardware processor is expected to be unable to communicate via the communication network; responsive to determining that the hardware processor is expected to be unable to communicate via the communication network, determine prefetch data to request prior to the hardware processor being unable to communicate via the communication network; request the prefetch data; receive and store the prefetch data prior to the hardware processor being unable to communicate via the communication network; and subsequent to the hardware processor being unable to communicate via the communication network, process the prefetch data with an application responsive to processing a first user input with the application.

RELATED APPLICATIONS

Any and all applications for which a domestic priority claim is identified in the Application Data Sheet of the present application are hereby incorporated by reference under 37 CFR 1.57.

BACKGROUND

Many mobile device applications are run on client devices that send and receive data in real-time. As a result, these mobile device applications generally become unusable without an active Internet connection. Even with improvements to cellular coverage and a surge in Wi-Fi hotspots, mobile device users often complain about network fluctuations, especially in crowded places or while travelling. Even in metropolitan cities, the continuity of the network connections may not be perfect. With unreliable networks, limited bandwidth, and high latency, some mobile device applications are difficult for mobile device users to enjoy.

Additionally, geofencing is a technology that enables mobile device applications to trigger an alert or action when a mobile device enters, leaves, or stays in certain virtual geographic boundaries, also known as a geofence.

SUMMARY

In some embodiments, an electronic device is disclosed for intelligently prefetching data via a computer network. The electronic device can include a device housing, a user interface, a memory device, and a hardware processor. The user interface can receive multiple user inputs from a user. The memory device can store an application. The hardware processor can: communicate via a communication network with multiple systems; determine that the hardware processor is expected to be unable to communicate via the communication network; responsive to determining that the hardware processor is expected to be unable to communicate via the communication network, determine prefetch data to request prior to the hardware processor being unable to communicate via the communication network; request the prefetch data from one of the multiple systems via the communication network; receive the prefetch data via the communication network and store the prefetch data to the memory device prior to the hardware processor being unable to communicate via the communication network; and subsequent to the hardware processor being unable to communicate via the communication network, process the prefetch data with the application responsive to processing a first user input of the multiple user inputs with the application.

The electronic device of the preceding paragraph can include one or more of the following features: The hardware processor can determine the prefetch data to request by determining application data that is likely to be utilized by the application upon processing of a second user input of the multiple user inputs which is received subsequent to the hardware processor being unable to communicate via the communication network. The hardware processor can determine the prefetch data to request from a second user input of the multiple user inputs this is not processed by the application. The first user input can include a request to activate a feature of the application. The hardware processor can, subsequent to the hardware processor being unable to communicate via the communication network, process the prefetch data with the application for the first time responsive to processing the first user input with the application. The hardware processor can: determine when and for how long the hardware processor is expected to be unable to communicate via the communication network; and determine the prefetch data to request according to when and for how long the hardware processor is expected to be unable to communicate via the communication network. The hardware processor can determine from a second user input of the multiple user inputs that the hardware processor is expected to be unable to communicate via the communication network. The second user input can include a request to enter a mode in which wireless communications controlled by the hardware processor are disabled and the user interface continues to be active and usable by the user. The second user input can include an indication that the user intends to transport the device housing to a geographic location where the hardware processor is unable to communicate via the communication network. The hardware processor can use the second user input to generate a calendar event which indicates the geographic location as a place which the user is planning to visit or likely to travel through with the device housing. The electronic device includes a power source that can supply energy to the hardware processor, and the hardware processor can determine from an energy level of the power source that the hardware processor is expected to be unable to communicate via the communication network. The hardware processor can determine from a data message received via the communication network that the hardware processor is expected to be unable to communicate via the communication network, the data message being generated by a remote server and indicating a prediction that the hardware processor is expected to be unable to communicate via the communication network. The hardware processor can: determine a geographic location of the hardware processor; and determine from the geographic location that the hardware processor is expected to be unable to communicate via the communication network. The hardware processor can determine from a bandwidth associated with the communication network that the hardware processor is expected to be unable to communicate via the communication network.

In some embodiments, a method is disclosed for intelligently prefetching data via a computer network. The method can include: receiving, by a user interface of a mobile device, multiple user inputs from a user; storing an application to a memory device of the mobile device; and under control of a hardware processor: determining that the hardware processor is expected to be unable to communicate via a communication network; in response to determining that the hardware processor is expected to be unable to communicate via the communication network, determining prefetch data to request prior to the hardware processor being unable to communicate via the communication network; requesting the prefetch data from one of multiple systems via the communication network; receiving the prefetch data via the communication network and storing the prefetch data to the memory device prior to the hardware processor being unable to communicate via the communication network; and subsequent to the hardware processor being unable to communicate via the communication network, processing the prefetch data with the application for the first time responsive to processing a first user input of the multiple user inputs with the application.

The method of the preceding paragraph can include one or more of the following features: The determining the prefetch data to request can include determining application data that is likely to be utilized by the application upon processing of a second user input of the multiple user inputs which is received subsequent to the hardware processor being unable to communicate via the communication network. The first user input can include a request to activate a feature of the application. The method can further include determining when and for how long the hardware processor is expected to be unable to communicate via the communication network, and the prefetch data to request is determined according to when and for how long the hardware processor is expected to be unable to communicate via the communication network.

In some embodiments, non-transitory physical computer storage is disclosed. The non-transitory physical computer storage can include computer-executable instructions stored thereon that, when executed by one or more processors of a mobile device, are configured to implement a process. The process can include: determining that the one or more processors are expected to be unable to communicate via a communication network; in response to determining that the one or more processors are expected to be unable to communicate via the communication network, determining prefetch data to request prior to the one or more processors being unable to communicate via the communication network; requesting the prefetch data from one of multiple systems via the communication network; receiving the prefetch data via the communication network and storing the prefetch data to a memory device prior to the one or more processors being unable to communicate via the communication network; and subsequent to the one or more processors being unable to communicate via the communication network, processing the prefetch data responsive to processing a first user input.

The non-transitory physical computer storage of the preceding paragraph can include one or more of the following features: A second user input can be used for determining that the one or more processors are expected to be unable to communicate via the communication network. The second user input can include a request to enter a mode in which wireless communications controlled by the one or more processors are disabled and a user interface of the mobile device continues to be active and usable by a user of the mobile device.

Although the electronic devices, methods, or processes described in the preceding paragraphs can determine that a processor may be expected to be unable to communicate and then take actions responsive to or before/after being unable to communicate, the electronic devices, methods, or processes can additionally or alternatively determine that a processor may be expected to have a limited ability to communicate (sometimes referred to as limited connectivity) and then take the actions responsive to or before/after having the limited ability to communicate. The expected limited ability to communicate can be caused by an expected limited bandwidth of a communication channel, an expected limited total amount of data that may be communicated via a communication channel, an expected limited reliability of a communication channel (for example, such that the communication channel unexpectedly or unpredictability ceases permitting communication), or an expected limited signal strength of a communication channel (for example, such that the communication does not support communication with a correctable number of errors), among other possibilities.

In some embodiments, a mobile device is disclosed for dynamically implementing geofences. The mobile device can include a device housing, a memory device, and a hardware processor. The memory device can store geofence data to define multiple geofences including a first geofence and a second geofence, the first geofence being associated with a different virtual geographic boundary from the second geofence. The hardware processor can be in communication with the memory device. The hardware processor can: obtain geofencing rules according to a data fetch policy, the geofencing rules indicating how to identify a first set of geofences with a first location and a second set of geofences with a second location; identify the first set of geofences to monitor from the multiple geofences according to the geofencing rules and the first location of the device housing, the geofencing rules indicating how to identify the first set of geofences with the first location; detect a change in location of the device housing from the first location to the second location; and identify the second set of geofences to monitor from the multiple geofences according to the geofencing rules and the second location.

The mobile device of the preceding paragraph can include one or more of the following features: The first set of geofences and the second set of geofences can be mutually exclusive. The first set of geofences and the second set of geofences can include a common geofence. The memory device can store the geofence data in a relational database. The memory device can store the geofence data in a geo-indexed database. The hardware processor can: detect another location change of the mobile device from the second location to a third location; and trigger a first action based at least in part on the third location satisfying first criteria of a first geofence of the second set of geofences.

BRIEF DESCRIPTION OF THE DRAWINGS

Throughout the drawings, reference numbers are re-used to indicate correspondence between referenced elements. The drawings are provided to illustrate aspects of the features described herein and not to limit the scope thereof.

FIG. 1 depicts an example computing environment for feature activation control and data prefetching.

FIG. 2 is a data prefetch process performable in the computing environment of FIG. 1.

FIG. 3 is a diagram of multiple example geofences that may be associated with an end user system in the computing environment of FIG. 1.

FIG. 4 illustrates an example geofencing rules management process performable in the computing environment of FIG. 1.

FIG. 5 illustrates example components usable to construct one or more of the devices, systems, or servers in the computing environment of FIG. 1.

DETAILED DESCRIPTION Introduction

Geo-fencing technology can be implemented in numerous practical applications. For example, geo-fencing can be implemented in drone management (for instance, a sporting event can use geo-fencing to create a temporary no-fly zone that prevents drones from crossing a defined perimeter), fleet management (for instance, geo-fencing can alert a dispatcher when a truck driver breaks from his route), compliance management (for instance, network logs can record geo-fence crossings to document the proper use of devices and their compliance with established policies), asset management (for instance, a network administrator can set up alerts so that when a hospital-owned mobile device leaves the hospital grounds, the administrator can monitor the device's location and lock it down to prevent it from being used), marketing (for instance, a company may send real-time, limited-time product offers or personalized promotions to a consumer's mobile device when the mobile device enters a defined geographical area to encourage immediate actions or buying by a user of the mobile device), human resource management (for instance, an employee's smart card can send an alert to security if the employee attempts to enter an unauthorized, geo-fenced area), law enforcement (for instance, an ankle bracelet can alert authorities if an individual under house arrest leaves the premises), or home automation (for instance, when the home owner's smartphone leaves the home's geo-fenced perimeter, the thermostat lowers itself to a set temperature).

While geofencing has numerous applications, the maximum number of active geofences is generally restricted. For example, iOS SDK prevents any single mobile application from monitoring more than 20 geofences concurrently, and Android restricts a particular mobile device from monitoring more than 100 geofences concurrently. Geofencing also can create a performance or a battery penalty on a mobile device.

Conventionally, there are limits on how many geofences a mobile device, or a mobile application running on a mobile device, can monitor simultaneously. Systems, methods, and apparatuses described herein may solve this or other problems by dynamically activating geofences “just in time.” As a mobile device is moved, the set of geofences monitored by the mobile device is changed to include those geofences that the mobile device is closest to or otherwise more likely to utilize. In this way, a particular geofence is monitored when it is likely to be triggered by the location of the mobile device, but may be deactivated (for instance, not monitored) when it will not, or is unlikely to, be triggered by the device location. As a result, systems, methods, and apparatuses described herein can provide for a hyper-personalized experience, such as based on the location of the mobile device or one or more other conditions. Moreover, the features described herein can facilitate a reduced processing burden, increased computational efficiency, or better responsiveness for or by the mobile device as the mobile device dynamically and responsively requests and processes data.

As an example, assume that 1000 geofences are associated with a particular mobile app, and further assume that the mobile application is prevented (for instance, by an operating system of the mobile device) from monitoring more than 20 geofences simultaneously. Systems, methods, and apparatuses described herein can filter using a set of rules (sometimes referred to as geofencing rules) the list of 1000 geofences down to those geofences that are more likely to be utilized. For example, the set of rules can be used to filter the list down to a subset that have boundaries within a threshold distance (for instance, a 500 m radius) from the location of the mobile device or are otherwise more likely to be utilized. In this way, a subset of the 1000 geofences (and in this case, 20 or fewer) may be monitored (for example, activated). The threshold distance can be configurable so that an administrator can adjust the size of the subset or monitoring as desired. Other characteristics can also be used for the set of rules, such as determined-associations, a time-of-time, among other possibilities.

In an implementation that includes filtering based on a threshold distance, as the location of the mobile device is changed, the filtering can be updated such that any geofences that are no longer within the threshold distance or are otherwise less likely to be utilized are deactivated (for instance, removed from monitoring) and any geofences that are now within the threshold distance, but previously were not within the threshold distance, or are otherwise more likely to be utilized are activated (for instance, monitored).

Points of interest to be monitored can be added to a lightweight relational database, which may contain a geo-index. The relational database can desirably further reduce the processing required to filter the list of potential geofences (which may, in some cases, be quite large). The results of the filter can be more quickly returned, for example, based on the latitude and longitude of a geofence to be monitored than using some other filtering approaches. Furthermore, storing geofences in a relational database, such as a geo-indexed database, can reduce the performance impact on the mobile device when working with large volumes of geofences.

By dynamically selecting which geofences are monitored based on the location of the mobile device, the limits on how many geofences a mobile device can monitor at a given time can be effectively bypassed or avoided. Furthermore, by monitoring those geofences that have boundaries within the configurable distance or are otherwise more likely to be utilized, geofences are less likely to be monitored when they have little to no chance of being triggered, thereby potentially freeing up geofence monitoring “slots” for other mobile applications on the mobile device. Further still, such a dynamic selection of geofences can reduce battery consumption of the mobile device since the mobile device may not “wake” the mobile application as frequently to deliver location updates.

A mobile device can, in certain implementations, prefetch data so that the mobile device may operate (potentially fully operate) without a network connection or with an inconsistent network connection. The mobile device can execute an application which is designed around the function of data (for instance, geo-location targeting rules) and may use native latitude-longitude data to evaluate rules and provide in-application experiences. The prefetching can be triggered by a variety of sources, such as local or remote to the mobile device, and responsive to data, such as local geo-locational data for the mobile device, user behaviors or interactions with the mobile device, or responsive to prompting from a server-side resource. For example, the mobile device can reach an edge of a geo-fence (which may, for instance, occur when a user of the mobile device walks into an airport), a user of the mobile device switches the mobile device into an airplane mode (such as may be defined or required by a government agency like the U.S. Federal Aviation Administration), or the Wi-Fi connection for the mobile device is connected or disconnected. A server-side prediction may trigger a prefetching of data due to a predicted outcome (for instance, a user may be driving down a road and about to hit an area with no cell service, so the mobile device can be instructed by a received server-side prediction to prefetch particular data)

The data prefetched by a mobile device can include device rules (for instance, geofences in an IF/THEN format, such as in a script file like JavaScript Object Notation), contextual information or small databases (for instance, subsets of customer or product databases or similar relational datasets), or content and media (for instance, images, videos, audio or other media files).

One example of the features described herein includes geo-triggered media loading. As a user of a mobile device may walk into an airport, the mobile device can detect the entry into the airport and accordingly automatically download media for an offline experience on the mobile device for the user. For instance, an audio or video subscription service installed or setup on the phone may automatically download a next 10 songs in a playlist or videos determined to be of interest to the user.

Another example of the features described herein includes predictive advertisement loading. A server-side predictive model can detect that a mobile device operated by a user may be likely to go offline. The server-side predictive model may predict that the mobile device may be likely to go offline because the user may be known to ride the subway most days at a consistent time. The server-side predictive model can moreover predict that the user often plays a game application while offline. A server running the server-side predictive model can thus send a trigger for the mobile device or the game application to download media data (for instance, images) and rules to the mobile device so that the game application may display advertisements while the mobile device is offline.

Yet another example of the features described herein includes predictive map generation. A route can be loaded (which can include or be used as pre-fetch rules) to a mobile device, and as the mobile device nears a geo-fence, the mobile device can prefetch the map images to attempt to ensure continued display experiences while the mobile device is travelling through an area known for lacking network service.

Yet a further example of the features described herein includes rules-based data loading for servicing remote locations. A customer relationship management (CRM) system can track appointments for a care provider who is scheduled for a house visit in a rural area. Prior to the house visit, a medical device in communication with the CRM system can prefetch a CRM dataset (for instance, patient health history) so that the care provider may have the CRM dataset available despite a network connection for the mobile device during the house visit. This may be coupled with a predictive model that can recommend additional data for prefetching, such as medical journals or guides, and that may be selected or determined based on a patient's symptoms collected prior to the care provider's arrival. The care provider may accordingly have the CRM dataset and other information that may prove relevant but might be otherwise unavailable during the house visit due to an unavailable or unreliable network connection by the mobile device.

Overview

With unreliable networks, limited bandwidth, and high latency, it is desirable for features of a mobile device to be functional, regardless of network connectivity. Generally, for a feature (such as an application running on the mobile device) to function in an unsteady or offline environment, the data that the application uses may be persisted locally on the mobile device for subsequent lookups. However, given an increasing number of applications installed on a typical smartphone, it can be impractical for a mobile device, such as a smartphone, to locally store all of the data associated with each application installed on the mobile device. And even if the mobile device did store all of the data for each application, at least some of the stored data may become stale.

Embodiments of the disclosed technology can utilize techniques for identifying that a mobile device may have limited or be without network connectivity and then pre-emptively (sometimes referred to as prefetching) download data relating to one or more applications likely to be used by the mobile device during limited or unavailable network connectivity. In this way, the one or more applications may be available for use (potentially with full capabilities) on the mobile device when requested, regardless of network connectivity, thereby improving the user experience of the mobile device.

Real-time interactions with a server can allow a mobile device to retain, or have access to, the latest and most-updated information. Accordingly, when a network is available and notwithstanding considerations such as cost of data usage, it can generally be desirable to retrieve data over the network just-in-time rather than to pre-emptively download the data for offline use. To balance the desire for obtaining the latest and most-updated information with the potential for limited or lost network connectivity, embodiments of the disclosed technology can utilize techniques for identifying a period of time when a mobile device may likely have limited or no network connectivity. The period of time can be imminent (for example, if a user provides an input to cause the mobile device to enter an airplane mode) or non-imminent (for example, a mobile device may not be expected to have network connectivity during a flight that a user is expected to take in a few days). Based on a determination that the mobile device may not have access to a reliable network, data for one or more features of the mobile device may be pre-emptively downloaded. In contrast, based on a determination that the mobile device may have access to a reliable network, data may not be pre-emptively downloaded.

In some cases, a mobile device can pre-emptively download the data at any time before the period of non-connectivity. For instance, continuing with the flight example above, the mobile device can download the data at any time, such as a random or periodic time, before the user's flight in a few days. In other instances, the mobile device can strategically determine when to prefetch the data. For example, the mobile device can download the data upon the occurrence of a particular event (for example, when the mobile device connected to Wi-Fi), in accordance with a particular schedule (for example, download the data at 3:00 AM, while the mobile device is unlikely to be in use by a user), or based on device or connectivity parameters (for example, download the data when device or data utilization is currently relatively low). By strategically prefetching the data, the mobile device can download the data at a time that may be less likely to inconvenience or take resources from the user of the mobile device.

The type of data that is prefetched can vary. For example, the prefetched data can include device rules (for example, one or more geofences), contextual information or small databases (for example, subsets of customer or product databases or similar relational datasets), or content and media (for example, images, videos, audio, or other media files). In some cases, the mobile device can determine which data to pre-emptively download.

Features disclosed herein therefore can include both (i) a determination of when a mobile device is expected to lose or have limited network connectivity and (ii) a determination of what data to prefetch in anticipation of a lost or limited network connectivity. The determinations can be made from or responsive to various inputs, including (a) behavioral data which may show an end user's plan or likelihood to leave network connectivity or to cause limited network connectivity for a mobile device, (b) device data which may reflect a characteristic of the mobile device, such as entering of a geographic area, an energy level of a power source of the mobile device, or monitored current network capabilities, that may suggest future limited network connectivity or loss of network connectivity for the mobile device, or (c) remote data generated by and received from a remote server and that can reflect processing by the remote server of the behavioral data or the device data for the mobile device as well as potentially behavioral data or device data from other mobile devices and that may suggest limited network connectivity or loss of network connectivity for the mobile device in the future. The output of the connectivity determination or data prefetch determination can be adjusted over time, such as by adjusting one or more algorithms used to control the determinations. In some implementations, the one or more algorithms can be adjusted by re-training or updated training (for instance, using the behavioral data, the device data, or the remote data or updates thereto) of a machine learning used to make the determinations.

User interfaces can be used to receive configuration inputs to control how or what data may be prefetched as described herein. The configuration inputs may be provided as part of deterministic, probabilistic, or measured instructions for controlling prefetching. The deterministic instructions can include rules that a configuration user may set based on known or fixed stages of navigation or behaviors by an end user. For instance, the deterministic instructions can indicate a desired action when an end user may be on step 3 of 4 of a funnel (such as through a webpage) or to preload a tracking pixel (sometimes referred to as a conversion pixel) on a check out form for a concluding page (such as a thank you page). The probabilistic instructions can include predictive triggers that a configuration user may set based on the behavioral data, the device data, or the remote data described herein. For instance, the probabilistic instructions can indicate a triggered action of preloading a live chat on step 3 of 4 of a funnel if an end user is predicted to be at least 90% likely to abandon the funnel. The measured instructions can include analytical threshold triggers based on data collected. For instance, the measured instructions can indicate a desired action responsive to a page load time satisfying an average load time threshold (such as 5 seconds) or responsive to a time on page satisfying a time on page threshold (such as 5 seconds). The user interfaces can be used to control monitoring of or actions associated with various characteristics, including those related to a device user (such as current historical [visitor], predicted values of the device user, or application session characteristics), content (such as device, location, time of day, referral, or channel source characteristics), or content (such as page, video, or screen characteristics).

Dynamic Feature Activation Control and Data Prefetching

FIG. 1 illustrates a computing environment 100 for implementing various features, including some or all of the feature activation control, data prefetching, and unsatisfactory network connection determination features, described herein. The computing environment 100 includes a network 108, an end user system 102, a configuration management user system 104, a content server 110, and a configuration control server 120. To simplify discussion, FIG. 1 illustrates one end user system, one configuration management user system, one content server, and one configuration control server, but multiple such systems or servers may be similarly used in the computing environment 100.

The end user system 102, the configuration management user system 104, the content server 110, and the configuration control server 120 may communicate with one another via the network 108. Although the network 108 is illustrated as one connected network, the network 108 can include multiple distinct or distributed networks. For example, the configuration management user system 104 can communicate with the configuration control server 120 via a separate and different network from the network that the configuration control server 120 uses to communicate with the end user system 102. The network 108 can include any type of communication network, such as one or more of a wide area network (WAN), a local area network (LAN), a cellular network, an ad hoc network, a satellite network, a wired network, a wireless network, a Wi-Fi network, a company intranet, the Internet, combinations of the same, or the like.

The end user system 102 can include any type of computing system. For example, the end user system 102 may include any type of computing device(s), such as a mobile device (for example, a laptop, smart phone, PDA, tablet, or the like), a desktop, a car-console device, a wearable device (for example, a smart watch or glasses with computing functionality), to name a few. The end user system 102 may include hardware and software components for establishing communications over the network 108. For example, the end user system 102 may be equipped with networking equipment and network software applications (for example, a browser) that facilitate communications via one or more networks (for example, the Internet or an intranet).

The end user system 102 can execute an application 103, such as with a processor of the end user system 102. The application 103 can be a browser or an application software (such as a native application or a progressive web application) that may be downloaded from an application marketplace or remote server (such as the content server 110) or received before receipt by the end user, stored on the end user system 102, and upon execution provide functionality to the end user system 102. The application 103 can collect and report data indicative of actions associated with the application 103. The actions can, for example, include a launching or closing of the application 103, collections of sensor data by the application 103, or end user interactions with the application 103.

The application 103 can operate according to policy rules 130 stored on the end user system 102. In one example, the policy rules 130 can include data that defines conditions or boundaries for one or more geofences. For example, the policy rules 130 can indicate how many or which geofences to monitor, when to trigger an event (for example, entrance and exit events), or geographical geofence boundaries. In another example, the policy rules 130 can include data that defines conditions for managing prefetching of data by the application 103 or the end user system 102, such as one or more conditions for triggering prefetching of data, one or more conditions usable for determining what data to prefetch upon determining to prefetch data, or how to process prefetched data prior to or subsequent to a loss of connection via the network 108.

The monitoring for a particular geofence can include processing of a geographic location of the end user system 102 by one or more applications installed on the end user system 102, such as the application 103. The processing can, for instance, facilitate a triggering of one or more determinations or actions based on or responsive to the geographic location of the end user system 102. The removal of monitoring for the particular geofence can result in the one or more applications no longer processing the geographic location of the end user system 102. Thus, the removal of monitoring for the particular geofence may mean that the one or more applications cease to be informed of the geographic location of the end user system 102 and accordingly may also no longer perform the processing associated with having access to the geographic location.

The application 103 or other application software installed on the end user system 102 can access one or more content pages of a content site or other content objects stored in content storage 112 of the content server 110. The content pages or content objects can be files or objects that may be accessed remotely and provided to the end user system 102. Accordingly, the content pages or content objects may be or include a media content, web pages, documents (such as pdf documents), videos, images, text, combinations of the same, or the like. The content server 110 may be a web server, an application server, a database server, combinations of the same, or the like.

The content server 110 can serve as an application marketplace from which the application 103 or updates thereto can be communicated to or downloaded by the end user system 102. The content server 110 can store content objects in the content storage 112. The content server 110 can transmit the content objects to the end user system 102 in response to a request for a content object or may push the content objects to the end user system 102.

The configuration control server 120 can include a configuration data storage 122 that may store configuration data for other devices, such as the end user system 102 or the configuration management user system 104. The configuration control server 120 can determine the configuration data by analyzing behavior or actions of the application 103, the end user system 102, or from analyzing traffic or data communicated on the network 108, as well as potentially behavior or actions of other applications or end user systems. Further, the configuration control server 120 can receive configuration data or updates thereto from the configuration management user system 104 to create or adjust the policy rules 130.

The configuration control server 120 can transmit or receive messages via the network 108, such as to or from the end user system 102 and or to or from configuration management user system 104. For example, the configuration control server 120 can transmit a message to one or both of the end user system 102 or the configuration management user system 104 providing or receiving the policy rules 130 or indications of or updates to the policy rules 130. The end user system 102 can implement the policy rules 130, such as part of rules engines, upon receipt. The configuration control server 120 can be implemented in computer hardware or software.

The configuration management user system 104 can include an application 105, such as a browser or an application software (such as a native application or a progressive web application), that can output an interface for presentation to a configuration user to permit the configuration user to create or adjust the policy rules 130. The application 105 may, for instance, can output a content page (such as a webpage) that may be provided by the configuration control server 120. The configuration management user system 104 can be any type of computing device including a mobile device (for example, a laptop, smart phone, PDA, tablet, or the like), a desktop, a car-console device, a wearable devices (for example, a smart watch or glasses with computing functionality), to name a few.

The configuration management user system 104 can be operated by configuration management users, such as marketing professionals, website operators, business users, operators of a content site or the content server 110, or any other individual who uses or manages mobile device policies, including for geofences or prefetching. The configuration management users may not be the end users of the application 103 in certain embodiments. The configuration management users can use the configuration management user system 104 to dynamically update the settings for mobile device policies, such as the policy rules 130.

FIG. 2 is a data prefetch process 200 illustrating an example mode of operation of the computing environment 100 of FIG. 1 and may be implemented by the various components shown in the computing environment 100. The data prefetch process 200 may in particular illustrate processing by the end user system 102 in collaboration with the configuration control server 120. For convenience, the data prefetch process 200 is described in the context of the computing environment 100, but may instead be implemented by other systems described herein or other computing systems not shown. Advantageously, in certain embodiments, the data prefetch process 200 provides an approach by which the end user system 102 may attempt to anticipate a disruption in network connectivity via the network 108 and prefetch data expected to be used by the end user of the end user system 102 during the disruption. The end user system 102 may look to behavior data, device data, or remote data to anticipate the disruption or determine handling of prefetching.

At block 202, the presence of the a trigger condition can be identified. For example, the end user system 102 can identify the presence of a trigger condition. The application 103 may, for instance, identify the trigger condition. The trigger condition can be determined from [i] behavioral data associated with the end user which be indicative of a likelihood that the end user will leave network connectivity or cause limited network connectivity for the end user system 102, [ii] device data which can reflect a characteristic of the end user system 102 that may suggest future limited network connectivity or loss of network connectivity for the end user system 102, or [iii] remote data generated by and received from another device and that can reflect processing by the another device of the behavioral data or the device data for the end user system 102 as well as potentially behavioral data or device data from other end user systems and that may suggest limited network connectivity or loss of network connectivity for the end user system 102 in the future. The trigger condition may be reported to the application 103 for identification, such as from a reported event (like an event detected and reported by another application or an operating system of the end user system 102 to the application 103) or a reported user input (like a user input detected by another application or an operating system of the end user system 102 and reported to the application 103), or determined by the application 103, such as from processing data like one or more user inputs to the application 103 or determining that data managed by the application 103 satisfies one or more criteria.

In general, the presence of the trigger condition can be linked with an unsatisfactory network connection for the end user system 102, such as an unsteady, weak, or missing signal connection. For example, the presence of the trigger condition can indicate that the end user system 102 may be likely to experience an unsatisfactory network connection at some point in the future (such as within a threshold period of time like 1 second, 2 seconds, 5 seconds, 10 seconds, 30 seconds, 1 minute, 2 minutes, 5 minutes, 10 minutes, 30 minutes, 1 hour, 2 hours, 5 hours, 1 day, 2 days, or 5 days or longer). The presence of the trigger condition may not mean that the end user system 102 will necessarily experience the unsatisfactory network connection. Rather, the presence of the trigger condition can indicate that the end user system 102 may have a set likelihood (such as with a 25%, 50%, or 75% probability) of experiencing the unsatisfactory network connection. The likelihood of the end user system 102 experiencing the unsatisfactory network connection can be determined by the end user system 102 using a predictive model or from predictive information or instructions received from the configuration control server 120. In other cases, the presence of the trigger condition indicates that the end user system 102 is expected with certainty or planned to experience the unsatisfactory network connection (such as within the threshold period of time).

A network connection can be considered unsatisfactory by the end user system 102 if one or more or all monitored connectivity parameters associated with the network connection fail to (or are expected to fail to) satisfy a connectivity threshold. The connectivity threshold can be based at least on any one or any combination of the connectivity parameters described herein. For example, the connectivity parameters can include one or more of a network bandwidth, a network speed, a download speed, an upload speed, a communication file size limit, a signal strength, a number of packets dropped, a bit rate, an error rate, a network generation, a network type, or the like.

The connectivity threshold may be considered to not be satisfied (and a network connection may thus considered to be unsatisfactory) if one or more of: the available bandwidth of a network does not satisfy a bandwidth threshold (for example, corresponding to a bandwidth level that is considered satisfactory for communication purposes), the available network speed does not satisfy a speed threshold, the available download speed does not satisfy a download speed threshold, the available upload speed does not satisfy a upload speed threshold, a file size to be transferred exceeds a communication file size limit or a set percentage thereof (for instance, 10%, 20%, 25%, 50%, 75%, or the like), the available signal strength does not satisfy a signal strength threshold, a number of packets dropped over a period of time satisfies a packets threshold, the bit rate does not satisfy a bit rate threshold, an error rate satisfies an error rate threshold, an available network generation (for example, 2G, 3G, 4G, 5G, LTE) does not satisfy a generation threshold, or a network type (for example, Wi-Fi, cellular, Bluetooth, etc.) does not match a desired network type.

On the other hand, a network connection can be considered satisfactory (or expected to be satisfactory) if the network connection is steady or online. Moreover, a network connection can be considered satisfactory if one or more or all monitored connectivity parameters associated with the network connection do (or are expected to) satisfy the connectivity threshold.

The trigger condition can vary across implementations. As an example, the trigger condition can correspond a scheduled event for an end user of the end user system 102, such as a meeting, an appointment, a lecture, a class, a concert, a movie, a flight, or the like. In some such cases, the end user system 102 can identify the presence of the scheduled event from a calendar or schedule associated with or managed via the end user system 102. For example, the end user system 102 can parse calendar data for the end user to identify the presence of one or more scheduled events.

As another example, the trigger condition can correspond to a particular location for the end user system 102. In some such cases, the end user system 102 can identify the presence of the trigger condition according to a location of the end user system 102. For example, the end user system 102 can identify the presence of the trigger condition by determining that the end user system 102 has entered a particular area or crossed over a particular geographic boundary. To make this determination, the end user system 102 can track or monitor the location of the end user system 102, such as using GPS, RFID, cellular data, Wi-Fi or another wireless connection protocol which may be incorporated in the end user system 102.

As yet another example, the trigger condition can correspond to one or more metrics and a metrics threshold for the end user system 102. In some such cases, the end user system 102 can identify the presence of the trigger condition by determining that the one or more metrics satisfies the metrics threshold. For instance, the one or more metrics can include a remaining energy level associated with a power source of the end user system 102. From determining that the remaining energy level does not satisfy an energy level threshold, the end user system 102 can identify the presence of the trigger condition.

As a further example, the trigger condition can correspond to a predictive trigger for the end user system 102. In some such cases, the end user system 102 can identify the presence of the trigger condition from a prediction that an event will happen for the end user system 102 or its end user. The predicted event can vary across implementations. For instance, the end user system 102 can predict that the end user system 102 will enter into a particular area or cross a particular geofence boundary. In another instance, the end user system 102 can predict that the end user of the end user system 102 is or will be navigating to or through an area with an unsatisfactory or limited connectivity network from an input to the end user system 102, such as the application 103 (which may be serving to provide navigation or communication functionality for the end user), that indicates the end user system 102 may or will likely enter into the area.

As yet a further example, the trigger condition can correspond to a connectivity threshold associated with a network connection for the end user system 102. In some such cases, the end user system 102 can identify the presence of the trigger condition by determining that a network connection is lost (for example, no network connection is available or for the end user system 102 is not connected to the network 108) or terminated (for example, by turning on an airplane mode or turning off cellular data for the end user system 102).

As an additional example, the trigger condition can correspond to a user action with the end user system 102. For example, if the user action is providing a user input to the end user system 102 to place the end user system 102 in an airplane mode, the end user system 102 can identify the presence of the trigger condition from receiving the user input.

At block 204, data to prefetch can be identified. For example, the end user system 102 can identify data to prefetch. The end user system 102 may determine to identify the data to prefetch responsive to the end user system 102 identifying the presence of the trigger condition at block 202. The data to be prefetched by the end user system 102 can include device rules (for instance, geofencing rules), contextual information or small databases (for instance, subsets of customer or product databases or similar relational datasets), content and media (for instance, images, videos, audio, or other media files), or advertisement data, among other possible data.

The end user system 102 can identify the data to prefetch according to a data prefetch policy. For example, the data prefetch policy can indicate which data to prefetch (such as how to select or determine data for prefetching or how much data to prefetch or whether to prefetch a particular batch of data for multiple different applications that is designated to be prefetched upon satisfaction of a particular condition), when to prefetch the data (such as upon occurrence of an event or at a set time that may be based on a prediction of how soon the end user system 102 may lose or have limited connectivity and how soon the end user system 102 may be expected to present the prefetched data), how to prefetch the data (such as which source from which to request the data or how to structure a request for the data), how to process the prefetched data (such as to delay processing or process immediately upon receipt), or the like. The data prefetch policy can indicate to prefetch data which is predicted to be used by the end user of the end user system 102 in the future. The data prefetch policy can be determined from the policy rules 130 and may be determined with or without input from the end user.

The end user system 102 can identify the data to prefetch from various inputs, such as the input data described with respect to block 202, including [i] behavioral data associated with the end user which can be indicative of a likelihood of the end user to leave network connectivity or cause limited network connectivity for the end user system 102 or what action or activity the end user may use the end user system 102 for during the time of limited or no network connectivity, [ii] device data which can reflect a characteristic of the end user system 102 that may suggest future limited network connectivity or loss of network connectivity for the end user system 102, including a potential duration of the time of limited or no network connectivity or an indication of what action or activity the end user may use the end user system 102 for during the time of limited or no network connectivity, or [iii] remote data generated by and received from another device and that can reflect processing by the another device of the behavioral data or the device data for the end user system 102 as well as potentially behavioral data or device data from other end user systems and that may suggest what data to prefetch in anticipation of the time of limited or no network connectivity. The various inputs can be input to one or algorithms, which provide identifications of the data to prefetch as an output.

At block 206, the data identified at block 204 can be requested. For example, the end user system 102 can request the data to be prefetched via the network 108 from another device, such as the content server 110.

At block 208, the data identified at block 204 can be received. For example, the end user system 102 can receive the data to be prefetched via the network 108 from the another device, such as the content server 110. The content server 110 may have used the request from the end user system 102 to retrieve the data to be prefetched from the content storage 112 and then transmitted the data to be prefetched via the network 108.

At block 210, the data identified at block 204 can be processed. For example, the end user system 102 can process the data to be prefetched by storing the data to be prefetched to a memory device for later use by the application 103, such as after the end user system 102 experiences limited or loss of network connectivity. The data to be prefetched may be processed by the application 103 responsive to processing a user input with the application 103, but may not be processed prior to processing the user input with the application 103. The data to be prefetched may be processed by the application 103 after the end user system 102 experiences limited or loss of network connectivity and not before the end user system 102 experiences limited or loss of network connectivity.

Data Prefetch Example Implementations

As a first example implementation of the data prefetch process 200 of FIG. 2, the end user system 102 can pre-emptively download media before the end user of the end user system 102 attends an event (such as boards a flight). The end user system 102 can identify the presence of a trigger condition, which can be an event (for instance, the flight) being set, scheduled, or upcoming for the end user, by determining from calendar data, email confirmation, or interaction with an event application that the end user is scheduled for the event.

Responsive to identifying the presence of the trigger condition, the end user system 102 can identify data to prefetch. The data to prefetch can include media, such as videos (for example, that a user may want to watch during the flight), songs in a playlist, or advertisements for presentation during or between the videos or songs, or other data that the user may be expected to be presented during the event. The end user system 102 may identify a period of time associated with the event, which can include an event duration (for instance, from the boarding pass or boarding/landing time), as well as a buffer period (which may be customized to an expected behavior by the end user, such as typical event arrival times) prior to the event to account for an early arrival to the event by the end user.

The end user system 102 may determine when to prefetch the data, such as a time or range of times in which to download. For instance, the end user system 102 can determine to prefetch the data when the end user system 102 may have or at least typically have a robust or consistent network connection (for example, at 4:00 AM when the end user may likely be sleeping and the end user may have access to a Wi-Fi connection) or at a set amount of time prior to the period of time when the end user system 102 is expected to experience limited or loss of network connectivity via the network 108 (for example, 12 or 24 hours in advance). The end user system 102 may delay completing performance of certain user-requested actions, such as actions that may adversely impact an ability of the end user system 102 to successfully prefetch the data (for example, entering an airplane mode responsive to a user input to enter an airplane mode), until the end user system 102 successfully prefetches the data.

As a second example implementation of the data prefetch process 200 of FIG. 2, the end user system 102 can pre-emptively download geofence rules or user data prior to, or upon, entering a particular geofence or location. The end user system 102 can identify the presence of a trigger condition, which can include the end user system 102 entering or passing through a location (for example, a boundary of a geofence), by determining that the end user is expected to be located in the location or that the user may be on track across the location (for instance, the end user may drive down a road with the end user system 102 and be approaching an area known to have no network connectivity, and the end user system 102 may automatically determine this approaching limited connectivity situation from directions being followed in a mapping application on the end user system 102) with the end user system 102.

The end user system 102 can identify data to prefetch, which can include geofencing rules or user data like map data. The end user system 102 may identify a period of time associated with the location, such as a period of time until or at which the end user system 102 is expected to reach the location, which can be used to control what or how much data may be prefetched. The end user system 102 can determine when to download the data, such to download the data once the end user system 102 is within a threshold distance from the location or to delay the download in order to avoid unnecessarily downloading data (for instance, if the end user happens to take a different route than expected).

As a third example implementation of the data prefetch process 200 of FIG. 2, the end user system 102 can pre-emptively download data in response to a user providing a command (for example, a user input) to switch the end user system 102 into an airplane mode (which can be a mode in which some or all wireless communication functions of the end user system 102 may be disabled).

The end user system 102 can identify the presence of a trigger condition, which can be the end user system 102 receiving or anticipating receiving a particular command indicative of the end user desiring to limit or disable network connectivity (for example, an airplane mode activation or activation of a menu one, two, three, or more steps prior to but likely to result in activation of the airplane mode).

The end user system 102 can identify data to prefetch, which can include media, advertisements, images, text, or the like, among other data. The end user system 102 can identify a period of time associated with the user input, which can be immediate or indicative of a change in a relatively short period of time in which the end user system 102 is expected to have limited or lost its network connection. The end user system 102 can determine when to download the data, which in this case may be immediately or within a threshold period of time (such as 0.5, 1, 2, 3, 5, 7, 10, 30, or 60 seconds or more). Notably, the end user system 102 may delay entry into the airplane mode for the purposes of completing the prefetch of data.

Geofencing Activation Control

The end user system 102 of FIG. 1, can pre-emptively download data in preparation for the end user system being without a network connection at some time in the future. In some cases, the data that is downloaded can relate to one or more features of a mobile application, such as geofencing technology features.

Geofencing technology can enable a mobile application on a mobile device to trigger an alert or action when the mobile device enters, leaves, or stays within in certain geographic boundaries, also known as geofences. Mobile application administrators can define the boundaries of the geofences (for example, by longitude and latitude or through user-created or Web-based maps), and the location of the mobile device can be monitored using GPS, RFID, cellular data, Wi-Fi or another wireless connection protocol. FIG. 3 is a diagram 300 illustrating a first geofence 302, a second geofence 304, a third geofence 306, and a fourth geofence 308 that may be associated with the end user system 102 of FIG. 1.

The end user system 102 can use a set of rules (sometimes referred to as geofencing rules) to filter a list of geofences down to those geofences that have boundaries within a threshold distance (for example, a 500 m radius) from the location of the end user system 102 or are otherwise more likely to be utilized. In this way, a subset of the geofences on the list of geofences (for example, 20 or fewer) may be monitored (for example, activated). The threshold distance can be configurable so that a configuration user of the configuration management user system 104 can adjust the size of the subset or monitoring as desired.

The geofencing rules can remain in place at the end user system 102 as the location of the end user system 102 changes. For example, the geofencing rules can indicate to update the filtering when the end user system 102 moves. In this way, the geofences can be updated such that any geofences that are no longer within the threshold distance or are otherwise less likely to be utilized are deactivated (for example, removed from monitoring) and any geofences that are now within the threshold distance, but previously were not within the threshold distance, or are otherwise more likely to be utilized are activated (for example, monitored).

To reduce the processing required to filter the list of potential geofences (which could, in some cases, be quite large) by the end user system 102, points of interest to be monitored can be added to a lightweight relational database, which may contain a geo-index. In this way, the results of the filter can be quickly returned, for example, according to the latitude and longitude of a geofence to be monitored. Furthermore, storing geofences in a relational database, such as a geo-indexed database, can reduce the performance impact on the end user system 102 when working with large volumes of geofences.

By dynamically selecting which geofences are monitored according to the geofencing rules, the limits on how many geofences the end user system 102 can monitor may be effectively bypassed or avoided. Furthermore, by the end user system 102 monitoring those geofences that have boundaries within the configurable distance or are otherwise more likely to be utilized, geofences are less likely to be monitored when they have little to no chance of being triggered, thereby potentially freeing up geofence monitoring “slots” for other mobile applications on the end user system 102. Further still, such a dynamic selection of geofences can reduce power consumption of the end user system 102 because the end user system 102 may not “wake” the mobile application as frequently to deliver location updates.

The end user system 102 can manage which geofences of the first geofence 302, the second geofence 304, the third geofence 306, and the fourth geofence 308 are monitored at a given time, and the management of geofences can be based at least on the location of the end user system 102.

As a first example, at a first point in time, the end user system 102 can be located at Location A. To manage which geofences are monitored at the first point in time, the end user system 102 can determine which geofences are within a threshold distance 330 from the end user system 102. In this instance, the threshold distance 330 can create a circular boundary 332 around the location of the end user system 102 (for example, Location A). As illustrated in FIG. 3, the circular boundary 332 can overlap with at least a portion of the first geofence 302, the second geofence 304, and the third geofence 306. And the circular boundary 332 may not overlap with the fourth geofence 308. In view of this, at the first point in time, the first geofence 302, the second geofence 304, and the third geofence 306 can be monitored, and the fourth geofence 308 can be inactive or not monitored.

As a second example, at a second point in time, the end user system 102 can be located at Location B. In this instance, a circular boundary 342 (created by a threshold distance 340) around Location B can overlap with at least a portion of the second geofence 304, the third geofence 306, and the fourth geofence 308. And the circular boundary 342 may not overlap with the first geofence 302. In view of this, at the second point in time, the second geofence 304, the third geofence 306, and the fourth geofence 308 can be monitored, and the first geofence 302 can be inactive or not monitored.

The threshold distance 330 or the threshold distance 340 can vary across. For example, the threshold distance 330 or the threshold distance 340 can be set by the end user system 102, the configuration management user system 104, or another system. In this way, the threshold distance 330 or the threshold distance 340 can be adjusted so that the size of the circular boundary 332 or the circular boundary 342 can be increased or decreased. This can allow the circular boundary 332 or the circular boundary 342 to capture more or fewer geofences. In some cases, the threshold distance 330 or the threshold distance 340 is dynamically updated so that the number of geofences captured within the circular boundary 332 or the circular boundary 342 may not be greater than a threshold amount. For example, iOS SDK prevents any single mobile application from monitoring more than 20 geofences concurrently. In some such cases, the threshold distance 330 or the threshold distance 340 can dynamically adjust so that the number of geofences captured within the circular boundary 332 or the circular boundary 342 may not be greater than 20.

The first geofence 302 is illustrated as a circular area defined by a radius around a point of interest 312, the second geofence 304 is illustrated as a rectangular area, the third geofence 306 is illustrated as a pentagonal area, and the fourth geofence 308 is illustrated as a triangular area. The location, shape, or size of the boundary of a geofence can vary across implementations. For example, the location of a point of interest, the location of a geofence, the shape of the boundary, or the size of the boundary can be set by the end user system 102, the configuration management user system 104, or another system.

Prefetching Geofencing Rules

Geofences can be controlled on mobile devices according to policy rules, such as geofencing rules. The geofencing rules can indicate which geofences are available, which geofences to monitor and when, how to select a set of geofences, when to activate or deactivate particular geofences, how many geofences can be active at a particular time, a scope or barrier associated with a geofence, or the like. In some cases, geofencing rules can update over time. For example, configuration management users can use the configuration management user system 104 to update the geofencing rules. As another example, the end user system 102 can pre-emptively download the geofence rules in preparation for the end user system being without a network connection at some time in the future.

FIG. 4 illustrates a geofencing rules management process 400. The geofencing rules management process 400 illustrates an example mode of operation of the computing environment 100 and may be implemented by the various components shown in the computing environment 100. For convenience, the geofencing rules management process 400 is described in the context of the computing environment 100, but may instead be implemented by other systems described herein or other computing systems not shown.

At block 402, policy rules can be obtained. For example, the end user system 102 can obtain the policy rules 130, which can include geofencing rules, or an update to the policy rules for the application 103 running on the end user system 102. The end user system 102 can obtain the policy rules 130 or an update thereto as part of a data prefetch policy or a data fetch policy. For example, the end user system 102 can pre-emptively download the policy rules 130 or an update thereto in preparation for the end user system 102 being without a network connection at some time in the future.

At block 404, a first set of geofences to monitor can be identified. For example, the end user system 102 can identify the first set of geofences to monitor from the geofencing rules and a first location of the end user system 102. The geofencing rules can indicate how to filter down a list of geofences associated with the application 103. The end user system 102 can use the geofencing rules and location data (for example, native lat/long location data) to determine which geofences are within a threshold distance from the first location. In this way, the end user system 102 can identify the first set and may activate or monitor the geofences of the first set.

At block 406, a location change can be detected. For example, the end user system 102 can detect a location change of the end user system 102 from the first location to a second location, such as from monitored GPS, RFID, cellular, Wi-Fi, or other location-identifying data.

At block 408, a second set of geofences to monitor can be identified from the location change detected at block 406. For example, the end user system 102 can identify a second set of geofences to monitor from the geofencing rules and the second location. The identification of the second set of geofences to monitor can be performed using a similar or the same approach as the approach used to identify the first set of geofences to monitor at block 404.

Example Computer System

FIG. 5 illustrates a computer system 500 usable to construct one or more of the devices, systems (for example, the end user system 102 or the configuration management user system 104), servers (for example, the content server 110 or the configuration control server 120), or the like within the computing environment 100 of FIG. 1.

As shown in FIG. 5, the computer system 500 can include (i) a processor(s) (CPUs) 510, (ii) an input/output device(s) 520 configured to allow users to input and output information and interact with the computer system 500 as well as transfer and receive data or capture data with one or more sensors, (iii) a read only memory device(s) (ROMs) 530 or equivalents to provide nonvolatile storage of data or programs, (iv) a display(s) 550 such as a computer monitor or other display device, (v) a network connection(s) 540 and a network interface(s) 542 configured to allow the computer system 500 to connect to other systems, servers, or portable devices, as well as a memory space(s) 560 and a database(s) 590. The database(s) 590 may be further divided or distributed as sub-database(s) 590A-590N, with the sub-database(s) storing feature or function specific information associated with a particular feature or function. The various components shown in FIG. 5 may be incorporated in a computer(s) 570. It is noted that the various components shown in FIG. 5, including the database(s) 590, are typically included as part of the computer(s) 570, however, they may be external to the computer(s) 570 in some aspects. For example, the database(s) 590 may be external to the computer(s) 570 and may be part of a separate database computer system or networked database system. In some instances, the computer system 500 may be a computing device like a desktop computer, mobile phone, or a server.

The memory space(s) 560 may include DRAM, SRAM, FLASH, hard disk drives, or other memory storage devices, such as a media drive(s) 580, configured to store an operating system(s) 562, an application program(s) 564, and data 568, and the memory space(s) 560 may be shared with, distributed with or overlap with the memory storage capacity of the database(s) 590. In some aspects, the memory space(s) 560 may include the database(s) 590 or in some aspects the database(s) 590 may include the data 568 as shown in the memory space(s) 560. The data stored in the memory space(s) 560 or the database(s) 590 may include information, such as event data, event processing rules, data processing routines, or other types of data described herein.

Additional Aspects and Terminology

Many other variations than those described herein will be apparent from this disclosure. For example, depending on the aspects, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (for example, not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain aspects, acts or events can be performed concurrently, for example, through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. In addition, different tasks or processes can be performed by different machines or computing systems that can function together.

As used herein, the terms “application” or “program,” in addition to having their ordinary meanings, can refer to an executable code that when executed by a hardware processor causes the hardware processor to perform operations in accordance with the executable code. In some instances, an application or a program, moreover, may refer to executable code that was previously compiled.

One or more parts of or all of the configuration control server 120 can be implemented in a distributed cloud platform that provides redundant or geographically dispersed access (for example, using a Multi-Content Delivery Network). Although not illustrated herein, the implementation of the distributed cloud platform can be similar in some respects to the distributed cloud platform described and illustrated with respect to FIG. 25 of U.S. Pat. No. 8,805,946, titled “SYSTEM AND METHOD FOR COMBINING CONTENT SITE VISITOR PROFILES,” which is incorporated by reference herein in its entirety.

One or more of the features, devices, servers, or systems described herein can be combined with or performed along with one or more of the features, devices, servers, or systems described in U.S. Pat. No. 8,843,827, titled “ACTIVATION OF DORMANT FEATURES IN NATIVE APPLICATIONS,” U.S. Pat. No. 9,363,311, titled “DELIVERY OF INSTRUCTIONS IN HOST APPLICATIONS,” U.S. Pat. No. 9,807,184, titled “CONFIGURATION OF CONTENT SITE USER INTERACTION MONITORING IN DATA NETWORKS,” and U.S. Pat. No. 10,327,018, titled “ENGAGEMENT TRACKING IN COMPUTER DATA NETWORKS.” The disclosures of the foregoing patents are hereby incorporated by reference in their entirety.

One or more user inputs described in this disclosure may be received using one or more different mechanisms. For example, user interface controls may be selected by a user using one or more input options, such as a mouse, touch screen input, or keyboard input, among other user interface input options. The user interface controls selected by the user can include one or more of buttons, dropdown boxes, select boxes, text boxes, check boxes, slider controls, or other user interface controls.

The various illustrative logical blocks, modules, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.

The various illustrative logical blocks and modules described in connection with the aspects disclosed herein can be implemented or performed by a machine, a microprocessor, a state machine, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A hardware processor can include electrical circuitry or digital logic circuitry configured to process computer-executable instructions. In another aspect, a processor includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.

The steps of a method, process, or algorithm described in connection with the aspects disclosed herein can be embodied directly in hardware, in a software module stored in one or more memory devices and executed by one or more processors, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art. An example storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The storage medium can be volatile or nonvolatile. The processor and the storage medium can reside in an ASIC.

Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain aspects include, while other aspects do not include, certain features, elements or states. Thus, such conditional language is not generally intended to imply that features, elements or states are in any way required for one or more aspects or that one or more aspects necessarily include logic for deciding, with or without author input or prompting, whether these features, elements or states are included or are to be performed in any particular aspect. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Further, the term “each,” as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term “each” is applied.

While the above detailed description has shown, described, and pointed out novel features as applied to various aspects, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, certain aspects described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. 

1-20. (canceled)
 21. An electronic device for intelligently prefetching data via a computer network, the electronic device comprising: a user interface configured to receive a plurality of user inputs from a user; a memory device configured to store an application; and a hardware processor configured to: receive an instruction via a user input of the plurality of user inputs, the instruction indicating to activate a mode in which wireless communications by the hardware processor via a communication network are disabled and the user interface continues to be active and usable by the user; responsive to receipt of the instruction and prior to activation of the mode, request prefetch data via the communication network; receive the prefetch data via the communication network; activate the mode subsequent to receipt of the prefetch data via the communication network; and process the prefetch data with the application responsive to processing a second user input of the plurality of user inputs.
 22. The electronic device of claim 21, wherein the communication network is a cellular network.
 23. The electronic device of claim 21, wherein the communication network is a Wi-Fi network.
 24. The electronic device of claim 21, wherein the mode is a mode in which all wireless communications by the hardware processor are disabled.
 25. The electronic device of claim 21, wherein the hardware processor is configured to: determine application data that is likely to be utilized by an application subsequent to the activation of the mode; and identify the prefetch data to request based on the application data.
 26. The electronic device of claim 21, wherein the hardware processor is configured to: determine a duration that the mode is expected to be active, and identify the prefetch data to request based on the duration.
 27. The electronic device of claim 21, wherein the request to activate the mode corresponds to a request to activate an airplane mode.
 28. A method for intelligently prefetching data via a computer network, the method comprising: receiving an instruction via a user input of a plurality of user inputs received by a user interface, the instruction indicating to activate a mode in which wireless communications by a hardware processor via a communication network are disabled and the user interface continues to be active and usable by the user; responsive to receipt of the instruction and prior to activation of the mode, requesting prefetch data via the communication network; receiving the prefetch data via the communication network; activating the mode subsequent to receipt of the prefetch data via the communication network; and processing the prefetch data with an application responsive to processing a second user input of the plurality of user inputs.
 29. The method of claim 28, wherein the communication network is a cellular network.
 30. The method of claim 28, wherein the communication network is a Wi-Fi network.
 31. The method of claim 28, wherein the mode is a mode in which all wireless communications by the hardware processor are disabled.
 32. The method of claim 28, further comprising: determining application data that is likely to be utilized by an application subsequent to the activation of the mode; and identifying the prefetch data to request based on the application data.
 33. The method of claim 28, further comprising: determining a duration that the mode is expected to be active, and identifying the prefetch data to request based on the duration.
 34. The method of claim 28, wherein the request to activate the mode corresponds to a request to activate an airplane mode.
 35. Non-transitory physical computer storage comprising computer-executable instructions stored thereon that, when executed by one or more processors of a mobile device, are configured to implement a process comprising: receiving an instruction via a user input of a plurality of user inputs received by a user interface, the instruction indicating to activate a mode in which wireless communications by a hardware processor via a communication network are disabled and the user interface continues to be active and usable by the user; responsive to receipt of the instruction and prior to activation of the mode, requesting prefetch data via the communication network; receiving the prefetch data via the communication network; activating the mode subsequent to receipt of the prefetch data via the communication network; and processing the prefetch data with an application responsive to processing a second user input of the plurality of user inputs.
 36. The non-transitory physical computer storage of claim 35, wherein the communication network is a cellular network.
 37. The non-transitory physical computer storage of claim 35, wherein the communication network is a Wi-Fi network.
 38. The non-transitory physical computer storage of claim 35, wherein the mode is a mode in which all wireless communications by the hardware processor are disabled.
 39. The non-transitory physical computer storage of claim 35, further comprising: determining application data that is likely to be utilized by an application subsequent to the activation of the mode; and identifying the prefetch data to request based on the application data.
 40. The non-transitory physical computer storage of claim 35, further comprising: determining a duration that the mode is expected to be active, and identifying the prefetch data to request based on the duration. 